bitkeeper revision 1.1717 (42b3442b7kXKhXN5lvR9spIGT5LsYQ)
authoriap10@tetris.cl.cam.ac.uk <iap10@tetris.cl.cam.ac.uk>
Fri, 17 Jun 2005 21:44:11 +0000 (21:44 +0000)
committeriap10@tetris.cl.cam.ac.uk <iap10@tetris.cl.cam.ac.uk>
Fri, 17 Jun 2005 21:44:11 +0000 (21:44 +0000)
commit227aeb4d79e2f90bae5048a26ebd6dc040a7d9f2
tree4c6efc63b5d443a5e6964711cf8cbb18b9960c1b
parent86d6165ed3685109216376bb183ff829036d5b40
bitkeeper revision 1.1717 (42b3442b7kXKhXN5lvR9spIGT5LsYQ)

When xend starts, it fires off xcs.  If you're running on a slow
machine its possible that xcs started but xend didnt wait long
enough to notice.  The attached patch loops several times while
waiting for xcs to come up.  It seems to be working here while the
original is not (slow machine here).

From: Tim Newsham [newsham@lava.net]
Signed-off-by: ian@xensource.com
tools/misc/xend